5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

ERROR


ERROR can be used in any event point in an input process to display an error message, or to print an error message in an output or action process.

(1) T/F execution conditions
(2) Error message (constant or TEMPn predefined field)

 

Using the Statement

Variable error messages can be displayed or printed by setting the predefined field TEMPn to the required message and entering TEMPn in place of a message in the ERROR statement.

When an error occurs, the image is redisplayed to the user with the error message blinking on line two of the status surface, and the terminal beeps. If more than one ERROR, WARNING, or MESSAGE statement is executed, the user can display the additional messages. The user must correct the problem before processing can continue with the next image.

In output processes, errors are printed on the report; in update, status, and subroutine processes errors are sent to the associated log. Each time an ERROR statement executes, the value of the predefined field ERRORS is incremented by one.

Related PDFs

ERRORS

Related Statements

WARNING, MESSAGE

Example

In this example, an ERROR statement followed by a BLINK statement are used to alert a user that the customer has exceeded their credit limit. 

Application Design Manual                                         "Powered by Appx Software"

1323

©2006 By APPX Software, Inc. All Rights Reserved